Archive Magazine CD 1995/Archive Magazine CD 1995.iso/text/hints/volume_05/issue_05

Text File | 1995-02-16 | 25.7 KB | 940 lines

Hints and Tips
5.5
•   A5000 PC delete danger – I found out the hard way that deleting the PC
directory (and probably Drive_C as well) gives a disc error over the
area of the deleted partition. The only solution is to reformat the hard
disc and restore the last backup. J.R.McLachlan, Hertford.
5.5
Yes, there does appear to be a problem here. The same thing happened to
us. In theory, the idea is that Drive_C is a filetype that is not
deleteable. The trouble is that on the A5000, it seems to get confused
and half delete it, leaving a blank entry in the file table (seen as a
blank line in the filer window if you use “full info”). The answer is to
change the filetype to, say, FFF with
5.5
*SETTYPE $.<pathname>.Drive_C FFF
5.5
before you try to delete it. Ed.
5.5
•   BBC Tracker Ball − In December’s Archive, Paul asked for a wiring
diagram to convert a BBC tracker ball to an Archimedes one. I have
converted an old Marconi tracker ball for use on the Archimedes using
the following diagram.
5.5
The nine wires come out of the bottom of the tracker ball socket as I
have drawn it. Socket 1 is marked, or it is on mine.
5.5
The connections are as follows...
5.5
   9-pin   Trackerball
5.5
   mini DIN   Socket
5.5
   1   3   yellow
5.5
   2   6   black
5.5
   3   7   brown
5.5
   4   9   grey
5.5
   5   2   orange
5.5
   6   1   red
5.5
   7   4   green
5.5
   8   8   white
5.5
   9   5   blue
5.5
The colours are the colours on mine. They may differ between various
tracker balls. A mark 1 Archimedes mouse lead will also fit this
particular tracker ball but two leads need swapping round.
5.5
Connectors 6 and 7, in my case red and brown, need to be changed over.
This can be accomplished with a needle by gently lifting the black
plastic clip above the connector with the needle whilst pulling gently
on the wire to be removed.
5.5
December’s article was, I think, for a mark 1 AMX mouse. I have a later
AMX mouse which is the same design as the early Archimedes mouse and the
lead is a straight swap.
5.5
Dave Morrell, Middlesbrough
5.5
•   Elite Cheat − Here is program that will create a commander file for
use with Elite. It gives you the most needed items to get around a
little better than before, especially the docking computer, (most
welcome). When you have successfully loaded it in, use galaxy map to see
where to go, a little bonus is waiting: Front beam laser, rear beam
laser, large cargo bay (35 tons), docking computer, E.C.M. system, four
missiles.
5.5
REM>:0.$.Elite_com
5.5
REM Program by Scott Edwards
5.5
REM 3-1-92
5.5
REM It is important that you have
5.5
REM the correct checksums on the
5.5
REM right line, the program will
5.5
REM inform you if you have a wrong line.
5.5
MODE0:OFF
5.5
DIM store% &1000
5.5
checkcode%=38901:code$=“”
5.5
line%=390:inc%=0
5.5
FOR l%=0 TO 17
5.5
FOR blk%=0 TO 15
5.5
READ code$
5.5
dat%=EVAL(“&”+code$)
5.5
checksum%=checksum%+dat%
5.5
?(store%+inc%)=dat%
5.5
PRINT dat%,~dat%
5.5
inc%+=1
5.5
NEXT
5.5
READ checkcode%
5.5
IF checksum%<>checkcode% THEN
5.5
PRINT “You have a data byte incorrect at ”;line%
5.5
STOP
5.5
ENDIF
5.5
line%+=10:finalcheck%=checksum%
5.5
checksum%=0
5.5
NEXT
5.5
IF finalcheck%=checkcode% THEN
5.5
PRINT“You have a correct file for saving”
5.5
REPEAT
5.5
INPUT“Enter the commander name for your file  ”;A$
5.5
UNTIL A$<>“”
5.5
SYS“OS_File”,10,A$,&C87,,store%, store%+&11C
5.5
ENDIF
5.5
PRINT“Program is Finished,now run ELITE and use your new commander”
5.5
END
5.5
:
5.5
REM Commander file for ELITE
5.5
:
5.5
DATA 16,B5,DC,72,DF,DD,20,C9,F2,3C, 54, EB,32,6F,EF,09,2244
5.5
DATA E5,F9,61,E3,31,12,B8,70,85,F3, FE,A9,EB,11,02,DD,2439
5.5
DATA 31,43,F2,80,D5,F6,81,FA,70,92, 9A, 72,B9,EB,FC,B9,2707
5.5
DATA C9,B1,42,CE,85,DD,F6,7F,5D,00, D2,9A,92,D2,6F,FC,2553
5.5
DATA B9,2F,F9,62,CF,B5,62,B8,7B,5E, 98,7E,AF,68,DC,AA,2413
5.5
DATA DD,39,30,CD,40,D6,B5,EF,53,70, 9E,91,E9,99,EC,DB,2568
5.5
DATA F1,2C,B1,50,C1,F5,4D,F7,EE,72, 97,52,A1,59,FC,A7,2558
5.5
DATA FD,78,B2,CD,22,CA,AD,FF,54,7F, 3D,52,67,0A,66,D7,2204
5.5
DATA F8,23,39,20,A2,B4,86,B4,6C,7D, 0B,1D,09,4A,D3,44,1663
5.5
DATA D3,37,3F,07,0F,06,A6,63,23,E3, 1D,18,84,80,84,D4,1541
5.5
DATA AA,8A,6B,10,8D,3B,39,43,EB,56, C6,B6,81,48,9F,1E,1846
5.5
DATA 9A,77,2C,64,DC,BA,A5,49,10,CE, BD,17,33,EF,5E,D4,2091
5.5
DATA A5,01,E8,E0,8D,12,71,30,6B,53, F9,F5,E9,47,02,B2,2110
5.5
DATA 91,37,22,7D,F1,F6,A4,7A,DC,C2, 9C,8A,B5,FE,7C,CB,2602
5.5
DATA 38,E2,DA,CF,49,E0,80,BF,CF,20, 6A,6E,E7,24,69,39,2207
5.5
DATA 7E,74,89,36,A6,69,0B,36,B7,A9, 33,46,99,DD,35,07,1676
5.5
DATA 34,D0,D6,93,1D,CF,F0,9B,03,0F, 61,EC,D6,13,E8,71,2181
5.5
DATA 48,83,01,29,F7,5A,82,75,32,A8, BA,41,00,00,00,00,1298
5.5
S Edwards, Stourbridge
5.5
•   First Word Plus 2 − In Archive 3.12 someone was bemoaning the lack of
a key that would toggle insert mode on and off. In fact the <insert> key
itself will do just that.
5.5
Robert Fuller, Basingstoke.
5.5
•   Lemmings Passwords − For all you bald headed insomniacs....
5.5
Taxing Level
5.5
02 Justforyou   03 Runandflee   04
Doortodoor
5.5
05 Stillalive   06 Fixedmyfix   07
Anurebevan
5.5
08 Helpmemate   09 Drinknwine   10
Tenpercent
5.5
11 Stickuptwo   12 DiginDelve    13
Hisbadluck
5.5
14 Teensforth   15 Teensfifth   16
Notsosweet
5.5
17 Driveukcar   18 Votesforme   19
Tenstonine
5.5
20 Doublesten   21 Lockandkey   22
Twoelevens
5.5
23 Justforme   24 Lemmingmore   25
Jiveanjive
5.5
26 Lemsinafix   27 Lemsheavon   28
Gardengate
5.5
29 Startowine   30 Fivexsixis
5.5
Mayhem Level
5.5
02 Nearlygone   03 Spendspree   04
Onthefloor
5.5
05 Uncleclive   06 Clogclicks   07
Difference
5.5
08 Waitanwait   09 Eatanddine   10
Tentontess
5.5
11 Binisthree   12 Twotimesix   13
Returntome
5.5
14 Twicelucky   15 Nineandsix   16
Charitynum
5.5
17 Stillyoung   18 Comesofage   19
Olderstill
5.5
20 Numbtwenty   21 Olderlemms   22
Lemminduck
5.5
23 Soonbefree   24 Lemmsstore   25
Lemmsdrive
5.5
26 Yourinafix   27 Lemtodevon   28Twostoplay
5.5
29 Oneafterme   30 Lemmgfinal
5.5
Robin Jefferies,  West Sussex.
5.5
•   Improving Logistix (v0.01) RISC-OS compatibility − As anyone who has a
copy of Logistix will be aware, the RISC-OS support files to “upgrade”
the package to run from the desktop do nothing except allow the
application to be launched from the desktop! (I do not know if there was
ever a subsequent release of Logistix since v0.01 − I assume not, as I
was a registered owner and was never informed of any update.)
5.5
In the case of old programs upgraded through the support disk, it’s
likely that some of the software houses did not have any real experience
of RISC-OS before the deadline date for the disk, so they may be excused
for the minimal level of compliance. (Acorn could not be considered to
have had any such excuse, but Logistix wasn’t actually written by them,
they only marketed it for Grafox.)
5.5
The directory structure of the “upgraded” !Logistix was rather messy,
and all pathnames were specific to the directory structure, therefore
not transportable from drive 0 and the $ directory. This makes it
impossible to install on a hard disk without some editing. The major
annoyance in using the application is that clicking on Logistix data
files does nothing except give an error message! Files can only be
loaded by first loading Logistix, then keyboarding through the menu
system.
5.5
The application directory can be arranged far better for RISC-OS by the
movement of a few files, and a little editing with !Edit. Dealing with
the directory structure first...
5.5
All that the user wants to see of Logistix is the !Logistix application
icon which can be double clicked on to start it. Your !System directory
should contain a directory called Modules which contains the latest
version of the FPE, Clib, Colours etc. As upgraded after using the
support disk, a Logistix floppy disk contains the following directories:
5.5
!System − A system folder which still requires updating with the RISC-OS
extras disk for the newer versions of Clib etc. (The latest Floating
Point Emulator (2.80) should also be placed in the Modules directory
inside this.)
5.5
!Logistix − The RISC-OS startup directory containing the !Boot,!Run and
!Sprites files.
5.5
Logistix − The actual Logistix program files and a (now outdated)
Floating Point Emulator.
5.5
MAKE A BACKUP COPY OF YOUR DISK then, using the backup copy...
5.5
Move the Logistix directory into the !Logistix directory.
5.5
Copy the latest FPEmulator you have into the !System.Modules directory.
5.5
(You may then delete the copy in the Logistix directory.)
5.5
Using !Edit, edit the !Logistix.!Boot file to contain the following
lines:
5.5
| !Boot for !Logistix version 0.01
5.5
| Updated to allow autoload
5.5
| (This is an OBEY file)
5.5
Set Logi$Dir <Obey$Dir>
5.5
IconSprites <Logi$Dir>.!Sprites
5.5
Set File$Type_DFF Logistix
5.5
Set Alias$@RunType_DFF Obey <Logi$Dir>.InitFile %%*0
5.5
Edit the !Run file so that it becomes:
5.5
| !Run for !Logistix version 0.01
5.5
| with better RISC-OS compatability
5.5
| (This is an OBEY file)
5.5
IconSprites <Logi$Dir>.!Sprites
5.5
WimpSlot -min 500k
5.5
RMEnsure FPEmulator RMLoad <System$Path>Modules.FPEmulator
5.5
Dir <Logi$Dir>.Logistix
5.5
LGX
5.5
The use of “<System$Path>Modules.” to reach the FPEmulator and setting
up the system variable <Logi$Dir> allow proper transportability of the
application, and it can now quite happily be installed anywhere in the
directory structure on a hard disk. Clicking on a data file causes RISC-
OS to check if a command has been matched to that file type. The system
variable Alias$@RunType _xxx has to be set up for files of the type in
question. If it has not been set up then you will get the error message
“No run action specified for this file type”. This is exactly what
happens with Logistix and similar applications written before (and even
since!) RISC-OS made its appearance. The addition of the line Set
Alias$@RunType_ DFF Obey <Logi$Dir>.InitFile %%*0 in the !Boot file
corrects the original omission, along with the following Obey file.
5.5
The file described here can be used with most applications which require
keyboard input to load files, the exceptions being those which clear the
keyboard buffer on start up. In principle, the method is simple. An Exec
file is used containing the commands or keystrokes to be executed as
though they had been entered at the keyboard. Due to the fact that only
Obey files can process the Obey$Dir system variable, it could get a
little bit confusing.
5.5
One way around this is from an Obey file:
5.5
1. Collect the startup pathname from RISC-OS and put it in a system
variable.
5.5
2. Using an Obey file, create an Exec file (by using Spool and Echo)
containing all the commands which require to be carried out to start the
application and set it up for a load operation.
5.5
3. Echo the system variable containing the full pathname into the Exec
file.
5.5
4. Exec the file which has just been created.
5.5
There is one small problem. When trying to write to the FIRST file being
created by a *Spool operation, extraneous data flows into it before the
data! A dummy file is spooled first to get rid of this before the real
file is created.
5.5
Using !Edit, create a new Obey file as follows, (You may miss out the
comment lines, but please leave in the fact that it is public domain and
attributed to me.)
5.5
| “InitFile” − Public Domain by
5.5
| D.Potter 26/6/90
5.5
| Allows keyboard emulated loading
5.5
| by double-clicking on a data file
5.5
| in the RISC-OS desktop.
5.5
| Intended in this version for
5.5
| Logistix, but the principal will
5.5
| work for other programs which do
5.5
| not clear the keyboard buffer at
5.5
| startup.
5.5
| This is an Obey File. (Exec files
5.5
| do not allow passing of system
5.5
| parameters.) To pass actual
5.5
| commands to Logistix, (or any
5.5
| similar application), an Exec file
5.5
| must be used.
5.5
| The Exec file is built by this
5.5
| file, including the full path for
5.5
| the startup file that was clicked
5.5
| on.
5.5
| The !Boot file for app. must be an
5.5
| Obey file containing the commands
5.5
|      Set Logi$Dir <Obey$Dir>
5.5
|      Set Alias$@RunType_xxx Obey <Logi$Dir>.InitFile %%*0
5.5
| (As well as any other commands
5.5
| already there)
5.5
| Where xxx is the filetype for the
5.5
| data file (DFF for Logistix).
5.5
| Logi$Dir will be the directory
5.5
| where the application resides, and
5.5
| is automatically set up when the
5.5
| application’s !Boot is first seen.
5.5
| Note : the | characters at the
5.5
| start of the above lines should
5.5
| NOT be in the !Boot file!
5.5
|
5.5
| Put the pathname information in
5.5
| temporary system variable Lload$
5.5
Set Lload$ %*0
5.5
| Clear extraneous data which
5.5
| appears when a file is written to
5.5
| at this stage by dummy spooling.
5.5
| This data is not needed here any
5.5
| more!
5.5
Spool <Logi$Dir>.!LoadFile
5.5
Echo <Lload$>
5.5
spool
5.5
| Now create the actual Exec file
5.5
| which will run LGX and issue the
5.5
| commands.
5.5
Spool <Logi$Dir>.!LoadFile
5.5
Echo || !LoadFile − Transient program built by InitFile
5.5
 (PD) by D.Potter 1990
5.5
Echo *Run <Logi$Dir>.!Run
5.5
|
5.5
| Send the Logistix load sequence −
5.5
| Note : NO SPACES in the sequence!
5.5
| /L = load, L= Logistix data file,
5.5
| <Lload$>= Full filename,
5.5
| A= All to be loaded  (You might
5.5
| want to use a different load
5.5
| sequence)
5.5
| (Where a return is required such
5.5
| as after the filename here,
5.5
| simply start a new Echo statement
5.5
| for the next command.)
5.5
|
5.5
Echo /LL<Lload$>
5.5
Echo A
5.5
|
5.5
| Close the file
5.5
Spool
5.5
|
5.5
| Set its file type
5.5
SetType <Logi$Dir>.!LoadFile Command
5.5
|
5.5
| Lose the temporary system variable
5.5
UnSet Lload$
5.5
|
5.5
| And run the file just created!
5.5
Exec <Logi$Dir>.!LoadFile
5.5
Save the above file as InitFile in the !Logistix directory.
5.5
Now click on the !Boot file in the !Logistix directory to set the system
variables. (You won’t always have to do this, as the !Boot file will be
run the first time you open the directory containing !Logistix. You only
need to do it at this time because you have been messing about with the
files, and the !Boot file may be different now than when it was last
run.) Clicking on any Logistix data file will now load Logistix and the
data file ready for use. You will still have to set up any default
prefixes etc.
5.5
It is not possible to do this automatically with a simple file such as
the above, because the full pathname would require to be split up to
provide the path to your file directory minus the filename. i.e. you
would require string handling facilities such as in Basic.
5.5
Note: The Logistix application itself still sets the CSD to the Logistix
directory within the !Logistix application directory. Implementing a
fully RISC-OS compatible version would require rewriting of the actual
coded LGX file, which is not possible without both the source code file
and the full approval of both Acorn and Grafox.
5.5
Other applications requiring a parameter block in memory − Other
programs (in Basic) written before RISC-OS, which will autoload a data
file at startup if a parameter block is set up in memory, could be made
to auto load using a version of the following routine. Again, this
builds an exec file which is run in Basic, using simple string handling
to split off the filename from the full pathname.
5.5
This example file was built to implement auto loading under RISC-OS on
an old BBC program which was written for DFS, and without re-writing
could not handle full pathnames, therefore it includes a line to set the
current directory to the application directory.
5.5
Note: This particular version works due to Basic being selected during
the execution of the Exec file and the memory accessible to both the
file and the program is that assigned by the selection of Basic. Any
other programs (e.g. integrated packages) which are to use the shared
parameter block must (obviously) use the same memory, so must not move
out of Basic (return to the desktop) in between the programs, but simply
chain each other.
5.5
This actual file will be irrelevant to most users, but it does show a
method of getting around the conversion of system variables to actual
data therefore easing the amount of work involved in conversion of BBC B
and Master programs to Archimedes. I know that re-writing the appli
cations might be more sensible, but this is aimed at people who know how
an application works, but didn’t write it in the first place!
5.5
|    “Autoload”
5.5
| A Customised version of “InitFile”
5.5
| −  Public Domain by D.Potter
5.5
|                             7/7/90
5.5
|       —— Information ——-
5.5
| Allows parameter block loading by
5.5
| double-clicking on a data file
5.5
| in the RISC-OS desktop.
5.5
| Intended in this version for the
5.5
| upgrade of an old BBC/Master
5.5
| program called Datbase, but the
5.5
| principal should work for other
5.5
| Basic programs which when started
5.5
| up check a parameter block in
5.5
| memory, and if found to be valid,
5.5
| will load the file referred to in
5.5
| the block.
5.5
| eg. Old “Integrated” suites of
5.5
| programs which allow files to be
5.5
| left as active or current for each
5.5
| program in the suite.
5.5
|
5.5
| This is an Obey File.
5.5
| An Exec file is built by this file
5.5
| including the filename for the
5.5
| startup file that was double
5.5
| clicked on.
5.5
| The !Boot file for app. must be an
5.5
| Obey file containing the commands
5.5
|       Set DatBa$Dir <Obey$Dir>
5.5
|       Set Alias$@RunType_xxx Obey <DatBa$Dir>.AutoLoad %%*0
5.5
| (As well as any other commands
5.5
| already there)
5.5
| Where xxx is the filetype for the
5.5
| data file. (DatBa$Dir will be set
5.5
| to the directory where the program
5.5
| & this file reside when the !Boot
5.5
| file is run)
5.5
|
5.5
| Put the full pathname information
5.5
| in system variable DBload$
5.5
Set DBload$ %*0
5.5
| Clear extraneous data which
5.5
| appears when a file is written to
5.5
| at this stage by dummy spooling.
5.5
| This data is not needed here
5.5
| anymore!
5.5
Spool <DatBa$Dir>.!LoadFile
5.5
Echo <DBload$>
5.5
spool
5.5
|
5.5
| Now create the actual Exec file
5.5
| which will run the program and
5.5
| load file.
5.5
Spool <DatBa$Dir>.!LoadFile
5.5
Echo || !LoadFile − Transient program built by AutoLoad
5.5
 (PD) by D.Potter 1990
5.5
Echo *Basic
5.5
Echo REM this particular application requires the CSD to be it -
5.5
Echo *Dir <DatBa$Dir>
5.5
Echo REM The startup parameter block for this application
5.5
 is at &F000, with
5.5
Echo REM the filename held at &F100, any conditions for
5.5
 printing at &F110,
5.5
Echo REM the record number to display at start up held in R%,
5.5
Echo REM and HIMEM held in H%
5.5
Echo HIMEM=&F000
5.5
Echo H%=&F000
5.5
|    Echoing a system variable
5.5
|    causes it to be converted to
5.5
|    the real data.
5.5
Echo F$=“<DBload$>”
5.5
Echo REM Split off the actual filename itself (This
5.5
 particular example is
5.5
Echo REM for conversion of a BBC B/
5.5
Master program which
5.5
 has restricted
5.5
Echo REM filename length, and therefore can’t handle
5.5
 full pathnames)
5.5
Echo REPEAT:F$=MID$(F$,INSTR(F$,“.”)+1):UNTIL INSTR(F$,“.”)=0
5.5
Echo $&F100=F$ : $&F110=“”:R%=1
5.5
Echo MO.12
5.5
Echo CHAIN“DATBASE”
5.5
|
5.5
| Where a return is required after a
5.5
| command such as L for load, simply
5.5
| start a new Echo statement for the
5.5
| next command − a return will be
5.5
| put in.
5.5
|
5.5
| Close the file
5.5
Spool
5.5
|
5.5
| Set its file type
5.5
SetType <DatBa$Dir>.!LoadFile Command
5.5
|
5.5
| And do it!
5.5
Exec <DatBa$Dir>.!LoadFile
5.5
Douglas Potter, Glasgow
5.5
•   Oak SCSI on A5000 − Using the ‘free’ menu option on a SCSI disc on the
iconbar doesn’t make use of the new Free module in the RISC-OS 3 ROM. To
correct this, include the following line in your hard disc boot file :
5.5
Set Alias$Free ShowFree -FS scsi %0
5.5
That’s all there is to it. Now, whenever you select ‘free’ from the SCSI
menu, a Free window pops up. The ‘%0’ picks up the device (disc drive)
name. Should you then subsequently wish to use Free from the command
line, use :
5.5
%Free [<disc spec>]
5.5
Typing ShowFree at the command line (with no parameters) reports the
command syntax.
5.5
David Lenthall, London
5.5
•   Refilling ink cartridges − We have, in past issues, published comments
about refilling inkjet cartridges with various types of ink. Tord
Eriksson sent in another such comment a while ago but I didn’t publish
it. He now writes....
5.5
Remember my recommending using water or fountain pen ink to keep your
printer going when your ink supply is gone? You didn’t publish it
(sensibly enough!) and I ran into deep trouble with it. I thought the
printhead was a goner (and messed it up further...), as the printer
didn’t work properly. After buying a new £100 head, with no improvement,
I found out that the reason you shouldn’t refill the cartridges is that
air easily leaks into the paint container if you disconnect it many
times (as when injecting ink) because the membrane gets worn. This means
that suction isn’t up to specification and you get uneven paint
delivery.
5.5
You may publish this as a warning − water does not harm a Canon BJ-what-
ever printer − but the side-effects can be very troublesome! I could
have spent the £100 on something more sensible!!!    Tord Eriksson,
Sweden  A
5.5
Impression Hints & Tips
5.5
•   Function key changes (cont’d) − In addition to Michael Ben-Gershon’s
excellent hint in Archive 5.2, p.12: Why not go the whole way and put
all those styles (like those fonts you use regularly to enhance your
texts) into your Impression default document, after you have assigned a
function key to each of them?
5.5
There are quite a lot of possibilities; in addition to those fields on
the function key strip that are quite empty, you can remove the default
styles you may not need (like hanging indent) and if there are some of
those ten scales offered which you never use, you can simply take over
those keys for your own styles.
5.5
You will find that the editable field which allows you to define a
keyboard short cut is slightly unusual: It accepts only certain entries
(function keys, <Shift>, <Return>,..), and it is not necessary to delete
the existing content with <Ctrl-U> − just click in the box, enter the
new combination and click on OK. (Don’t press <Return>, because that
simply means that the short cut for your style is the Return key!)
5.5
Jochen Konietzko, Köln, Germany
5.5
• Sprite files in Impression − Kevin Beales told us (Archive 5.4 p5)
about Impression’s ability to scale pictures in Draw format. In this
context, he forgot to mention something even more remarkable: Impression
can also scale sprites! This works in exactly the same way as he
described.
5.5
Of course, due to the well known problems of jagged edges/loss of
detail, you shouldn’t scale up or down too much; but if you have a
sprite that is just slightly too big or too small for its intended
place, then this feature of Impression is certainly extremely useful!
5.5
Jochen Konietzko, Köln, Germany
5.5
•   Illustrated Impression documents − I often include sprite and draw
files in my Impression documents (for test papers and the like).
5.5
One minor problem is that one can’t really edit those graphic frames in
an Impression document. Therefore, to have the corresponding files
always on hand, I save them into the document’s directory (after opening
a window on this directory by <shift>-double clicking).
5.5
This is one more reason for buying Compression: A typical sketch I make
with DrawPlus is reduced from about 6k to about 2 kbytes. A screen shot
made of an oscilloscope application I use takes up 100 kbytes; Compres
sion reduces this to just about 5k bytes (!). This means that even
pictures that appear in several documents don’t clog up the hard disk
too much, if you always save them together with the documents they
appear in.
5.5
(Surely, though, the Draw files are already in the Impression document
directory? Why not edit them directly from there? Two drawbacks, I
suppose... you don’t know which file is which because they have names
like Story2 and Story4 (but you could identify them if you have full
info set in the filer window because of their size) and secondly the
changes to the Drawfiles are only displayed then next time you load the
Impression document. Ed.)
5.5
(By the way: Can anyone tell me whether this hint will become obsolete
once Computer Concepts’ much vaunted Impulse II will be available, that
is, whether you will then be able to open a graphic file saved somewhere
by clicking on a graphic frame in an Impression document?)
5.5
Jochen Konietzko, Köln, Germany
5.5
•   Tiny left hand margin − I often wondered why the default document on
the Impression disc has a left hand margin set on the base style of a
couple of millimetres. Because of my sense of symmetry, I reduced that
to zero as soon as I started using Impression. Surely, if you create a
new master page with, say, 10cm margins, you don’t want the lefthand
margin to be 10.2cm?
5.5
Suddenly it dawned on me... yes, I know I’m slow... the reason for the
small lefthand margin is to make it easier to position the cursor to the
left of the first character on a line. If, as I do, you have zero margin
in the base style, you’ve got to judge the mouse cursor fairly accu
rately otherwise it goes onto the paper margin and turns into a hand.
Well, yer pays yer money... but I think I’ll stay as I am. I have too
many documents to change them all. Ed.
5.5
•   Impression speed users’ tips − I find that if you can get into the
habit of using <adjust> reverse scrolling, it really does save time,
especially when I am laying out the magazine and the screen is cluttered
with windows. Just press <select> to scroll down and switch quickly to
<adjust> to go back up again without having to move the mouse and locate
the other end of the scroll bar − which could be under another window
anyway.
5.5
Also, <adjust> can be extremely useful, again with a cluttered screen,
for moving windows whilst keeping them where they are relative to the
other documents. It takes practice, but it speeds things up in the long
run. Ed.  A
5.5